testing: initial implementation of continuous run #170770
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
First pass of #134941 The UI is pretty minimal so far, just a new icon (though I have a proposal for some changes in the UX channel.) If there's more that one profile that supports continuous test runs, then we open a quickpick and ask the user which ones they want to use. The data flow is then fairly simple. We call the `profile.runHandler` with the appropriate request, but just doesn't "track" it like we do for normal test runs. Then, any `createTestRun` calls are tracked as ordinary extension-triggered test runs. Currently we don't do anything to associate these new test runs with the fact that they were from a specific auto-run request, but that could be added if need to in the future.
connor4312
force-pushed
the
connor4312/testing-continuous-run
branch
from
4e30951
to
a308583
Compare
bpasero
approved these changes
Jan 8, 2023
humsarika
added a commit
to humsarika/vscode
that referenced
this pull request
Jan 8, 2023
testing: initial implementation of continuous run (microsoft#170770)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First pass of #134941
The UI is pretty minimal so far, just a new icon (though I have a proposal for some changes in the UX channel.)
If there's more that one profile that supports continuous test runs, then we open a quickpick and ask the user which ones they want to use.
The data flow is then fairly simple. We call the
profile.runHandlerwith the appropriate request, but just doesn't "track" it like we do for normal test runs. Then, anycreateTestRuncalls are treated as ordinary extension-triggered test runs.Currently we don't do anything to associate these new test runs with the fact that they were from a specific auto-run request, but that could be added if need to in the future.